Skip to content

Add personalized job feed backend with cache and external API integration#16

Open
cto-new[bot] wants to merge 1 commit intomainfrom
feature/job-feed-backend-linkedin-supabase
Open

Add personalized job feed backend with cache and external API integration#16
cto-new[bot] wants to merge 1 commit intomainfrom
feature/job-feed-backend-linkedin-supabase

Conversation

@cto-new
Copy link
Copy Markdown
Contributor

@cto-new cto-new bot commented Nov 13, 2025

Summary

Introduce a personalized job feed backend. It fetches listings from external sources (RapidAPI JSearch), caches results in Supabase with TTL, and serves role-aligned listings based on user profiles.

Details

  • Add Supabase migration 004_job_feeds.sql to create job_feeds cache with TTL, RLS policies, and search function
  • Implement lib/job-service.ts with cache-first fetch logic, TTL-based caching, data normalization, and cleanup
  • Create API route app/api/jobs/route.ts supporting authenticated, rate-limited, query-validated, personalized job fetch and cache cleanup (POST)
  • Define and export job schemas in types/jobs.ts and index.ts for centralized imports
  • Document backend with docs/JOB_FEED_BACKEND.md and docs/JOB_FEED_INTEGRATION_EXAMPLE.md
  • Update repository README to mention Job Feed integration
  • Add environment variable example (.env.example) for RapidAPI and app URL
  • Include a basic test scaffold for JobService under lib/tests/ (placeholder)
  • Adjust server-side client creation pattern to call createClient per method to avoid Next.js build issues
  • Add auxiliary documentation and notes for migration, security, and performance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants